We started with Patron. In round 2, we add the basic support for the Book. The book dao needs the same basic tests:
Creating a Book
Removing a Book
Updating a Bookadd
Note that we did not also include retrieving a book. We use this functionality in all of the tests anyway so I do not include a specific test for that functionality. This might seem like we’re not isolating tests perfectly but then I’ve never seen or come up with a “perfect” solution to this issue and this seems adequate to me.
We've already written a test very much like the above list if you consider PatronTest. We can extract quite a bit of common code out of our PatronTest and reuse it in our BookTest class. Take a look at this base class (note the embedded comments contain background information): BaseDbDaoTest.java
packagesession;importjavax.persistence.EntityManagerFactory;importjavax.persistence.Persistence;importorg.apache.log4j.BasicConfigurator;importorg.apache.log4j.Level;importorg.apache.log4j.Logger;importorg.junit.After;importorg.junit.Before;importorg.junit.BeforeClass;/**
* A base class for tests that handles logger initialization, entity manager
* factory and entity manager creation, associating an entity manager with a
* dao, starting and rolling back transactions.
*/publicabstractclass BaseDbDaoTest {private EntityManagerFactory emf;/**
* Once before the tests start running for a given class, init the logger
* with a basic configuration and set the default reporting layer to error
* for all classes whose package starts with org.
*/
@BeforeClass
publicstaticvoid initLogger(){// Produce minimal output.
BasicConfigurator.configure();// Comment this line to see a lot of initialization// status logging.Logger.getLogger("org").setLevel(Level.ERROR);}/**
* Derived class is responsible for instantiating the dao. This method gives
* the hook necessary to this base class to init the dao with an entity
* manger in a per-test setup method.
*
* @return The dao to be used for a given test. The type specified is a base
* class from which all dao's inherit. The test derived class will
* override this method and change the return type to the type of
* dao it uses. This is called **covariance**. Java 5 allows
* covariant return types. I.e. BookDaoTest's version of getDao()
* will return BookDao while PatronDao's version of getDao() will
* return Patron.
*/publicabstract BaseDao getDao();/**
* Before each test method, look up the entity manager factory, get the dao
* and set a newly-created entity manager and begin a transaction.
*/
@Before
publicvoid initEmfAndEm(){
emf = Persistence.createEntityManagerFactory("lis");
getDao().setEm(emf.createEntityManager());
getDao().getEm().getTransaction().begin();}/**
* After each test method, roll back the transaction started in the
*
* @Before method then close both the entity manager and entity manager
* factory.
*/
@After
publicvoid closeEmAndEmf(){
getDao().getEm().getTransaction().rollback();
getDao().getEm().close();
emf.close();}}
Now let’s see how this impacts the creation of our new BookTest class. We’ll start with everything but the tests and then look at each test.
Everything but the Tests
Here is the test class minus all of the tests.
packagesession;importstaticorg.junit.Assert.assertEquals;importstaticorg.junit.Assert.assertNotNull;importstaticorg.junit.Assert.assertNull;importjava.util.Calendar;importorg.junit.Test;importentity.Author;importentity.Book;importentity.Name;publicclass BookDaoTest extends BaseDbDaoTest {private BookDao dao;/**
* By overriding this method, I'm able to provide a dao to the base class,
* which then installs a new entity manager per test method execution. Note
* that my return type is not the same as the base class' version. I return
* BookDao whereas the base class returns BaseDao. Normally an overridden
* method must return the same type. However, it is OK for an overridden
* method to return a different type so long as that different type is a
* subclass of the type returned in the base class. This is called
* covariance.
*
* @see session.BaseDbDaoTest#getDao()
*/
@Overridepublic BookDao getDao(){if(dao == null){
dao = new BookDao();}return dao;}}
Creating a Book
We wrote this pretty much the same as in the Patron test. It might seem like we could get further reuse between tests and we could but at the cost of probably a bit too much indirection.
@Test
publicvoid createABook(){finalBook b = createABookImpl();finalBook found = getDao().retrieve(b.getId());
assertNotNull(found);}privateBook createABookImpl(){final Author a1 = new Author(newName("Bill", "Burke"));final Author a2 = new Author(newName("Richard", "Monson-Haefel"));return getDao().create("Enterprise JavaBeans 3.0", "978-0-596-00978-6",
Calendar.getInstance().getTime(), a1, a2);}
Removing a Book
This test method looks just like one in the PatronTest class. If you’re looking for an advanced exercise, consider moving all of the tests in the base class and making the derived class methods use them somehow. Warning, you might want to look up annotation inheritance.
@Test
publicvoid removeABook(){finalBook b = createABookImpl();Book found = getDao().retrieve(b.getId());
assertNotNull(found);
getDao().remove(b.getId());
found = getDao().retrieve(b.getId());
assertNull(found);}
Updating a Book
@Test
publicvoid updateABook(){finalBook b = createABookImpl();finalint initialAuthorCount = b.getAuthors().size();
b.addAuthor(new Author(newName("New", "Author")));
getDao().update(b);finalBook found = getDao().retrieve(b.getId());
assertEquals(initialAuthorCount + 1, found.getAuthors().size());}
Try to find a non- existant book
@Test
publicvoid tryToFindBookThatDoesNotExist(){finalBook b = getDao().retrieve(-1123123123l);
assertNull(b);}
Note that with the introduction of the base class we’ll also need to make changes to PatronTest. Here’s the updated version of PatronTest taking the new base class into consideration. PatronDaoTest.java Updated
packagesession;importstaticorg.junit.Assert.assertEquals;importstaticorg.junit.Assert.assertFalse;importstaticorg.junit.Assert.assertNotNull;importstaticorg.junit.Assert.assertNull;importorg.junit.Test;importentity.Address;importentity.Patron;/**
* This class has been updated to take advantage of BaseDbDaoTest. In reality, I
* just pulled the common functionality of pre test initialization and post test
* initialization to a base class since I'm going to use it across several test
* cases.
*/publicclass PatronDaoTest extends BaseDbDaoTest {privatestaticfinalString NEW_PN = "555-555-5555";private PatronDao dao;/**
* @see session.BaseDbDaoTest#getDao()
* @see session.BookDaoTest#getDao()
*/
@Overridepublic PatronDao getDao(){if(dao == null){
dao = new PatronDao();}return dao;}
@Test
publicvoid createAPatron(){final Patron p = createAPatronImpl();final Patron found = getDao().retrieve(p.getId());
assertNotNull(found);}/**
* I need to create patrons in several tests so it is factored out here.
*
* @return Newly created patron already inserted into the database under the
* current transaction
*/private Patron createAPatronImpl(){final Address a = new Address("5080 Spectrum Drive", "Suite 700 West",
"Addison", "TX", "75001");return getDao().createPatron("Brett", "Schuchert", "972-555-1212", a);}
@Test
publicvoid removeAPatron(){final Patron p = createAPatronImpl();
getDao().removePatron(p.getId());final Patron found = getDao().retrieve(p.getId());
assertNull(found);}
@Test
publicvoid updateAPatron(){final Patron p = createAPatronImpl();finalString originalPhoneNumber = p.getPhoneNumber();
p.setPhoneNumber(NEW_PN);
getDao().update(p);final Patron found = getDao().retrieve(p.getId());
assertNotNull(found);
assertFalse(NEW_PN.equals(originalPhoneNumber));
assertEquals(NEW_PN, p.getPhoneNumber());}
@Test
publicvoid tryToFindPatronThatDoesNotExist(){finalLong id = -18128129831298l;final Patron p = getDao().retrieve(id);
assertNull(p);}}
The Dao Classes
The BookDao looks a whole lot like the PatronDao: BookDao.java
packagesession;importjava.util.Date;importentity.Author;importentity.Book;/**
* This class offers the basic create, read, update, delete functions required
* for a book. As we implement more complex requirements, we'll be coming back
* to this class to add additional queries.
*/publicclass BookDao extends BaseDao {publicBook create(finalString title, finalString isbn,
finalDate publishDate, Author... authors){finalBook b = newBook(title, isbn, publishDate, authors);
getEm().persist(b);return b;}publicBook retrieve(finalLong id){return getEm().find(Book.class, id);}publicvoid remove(Long id){finalBook b = retrieve(id);if(b != null){
getEm().remove(b);}}publicvoid update(Book b){
getEm().merge(b);}}
Note that this class depends on a simple base class, the BaseDao, which offers support for storing the Entity Manager attribute: BaseDao.java
packagesession;importjavax.persistence.EntityManager;/**
* A simple base class for all dao's. It offers 2 features. First, it has the
* entity manager attribute. Second, it makes it possible to have a common test
* base class with the getDao() method to allow for automatic initialization.
*/publicabstractclass BaseDao {private EntityManager em;publicvoid setEm(final EntityManager em){this.em = em;}public EntityManager getEm(){return em;}}
And finally, here’s the updated PatronDao that has been rewritten to use the BaseDao. PatronDao.java
packagesession;importentity.Address;importentity.Patron;/**
* This class supports basic create, read, update, delete functionality for the
* Patron. As with Book, as we implement more requirements we'll be revisiting
* this class to extend its functionality.
*/publicclass PatronDao extends BaseDao {public Patron createPatron(finalString fname, finalString lname,
finalString phoneNumber, final Address a){final Patron p = new Patron(fname, lname, phoneNumber, a);
getEm().persist(p);return p;}public Patron retrieve(finalLong id){return getEm().find(Patron.class, id);}publicvoid removePatron(finalLong id){final Patron p = retrieve(id);if(p != null){
getEm().remove(p);}}public Patron update(final Patron p){return getEm().merge(p);}}
The Entity Model
We’ve added support for a Book and along the way we had to add in a few more classes. After the second test suite, we’re up to the following entities:
Entity
Description
Address
This entity represents the address for both an Author and a Patron. In the first tutorial we embedded this class. Now we’re allowing it to exist in its own table as a first-class citizen rather than embedding it.
Author
Books and Authors have a bi-directional, many to many relationship with each other. That is, a book has one to many Authors and an Author has one to many books. This entity represents one author and maintains a Set<Book> representing each of its books. We treat the Author as the secondary part of the relationship and the book as Primary.
Book
The book is a key entity in our system. It maintains a set of Authors and is considered the master of the bi-directional relationship. In version 1 of our system, the relationship between Books and Patrons is direct. We’ll change that in version 2.
Name
Authors and Patrons both have a name. Rather than duplicate the definition of names in both classes, we create a Name entity. This entity is embeddable, meaning its attributes will be stored as columns in the entities in which it is contained rather than as rows in a table all of its own.
Patron
The patron borrows books, so it has a Set<Books> as well as an embedded Name.
Now let’s review the code for each of these entities. As with previous examples, pay attention to the embedded comments.
Address
packageentity;importjavax.persistence.Column;importjavax.persistence.Entity;importjavax.persistence.GeneratedValue;importjavax.persistence.Id;/**
* This class will be known to JPA as an entity. It represents an address. It is
* a fairly simple class that gets stored in its own table called ADDRESS. The
* column names equal the names of the attributes.
*/
@Entitypublicclass Address {/**
* The next attribute is a key column in the database with a
* database-specific generated unique value.
*/
@Id
@GeneratedValue
privateLong id;/**
* The next attribute will be stored in a column with space for 50
* characters and cannot be null (the default)
*/
@Column(length = 50)privateString streetAddress1;/**
* The next attribute will be stored in a column with space for 50
* characters and it can be null(nullable = true).
*/
@Column(length = 50, nullable = true)privateString streetAddress2;
@Column(length = 20)privateString city;
@Column(length = 2)privateString state;
@Column(length = 9)privateString zip;public Address(){}public Address(finalString sa1, finalString sa2, finalString city,
finalString state, finalString zip){
setStreetAddress1(sa1);
setStreetAddress2(sa2);
setCity(city);
setState(state);
setZip(zip);}publicString getCity(){return city;}publicvoid setCity(finalString city){this.city = city;}publicString getState(){return state;}publicvoid setState(finalString state){this.state = state;}publicString getStreetAddress1(){return streetAddress1;}publicvoid setStreetAddress1(finalString streetAddress1){this.streetAddress1 = streetAddress1;}publicString getStreetAddress2(){return streetAddress2;}publicvoid setStreetAddress2(finalString streetAddress2){this.streetAddress2 = streetAddress2;}publicString getZip(){return zip;}publicvoid setZip(finalString zip){this.zip = zip;}publicLong getId(){return id;}publicvoid setId(Long id){this.id = id;}}
Author
packageentity;importjava.util.Set;importjavax.persistence.Embedded;importjavax.persistence.Entity;importjavax.persistence.GeneratedValue;importjavax.persistence.Id;importjavax.persistence.ManyToMany;/**
* I am an entity with a bidirectional relationship to Book. The Book is
* considered the master of the relationship.
*/
@Entitypublicclass Author {
@Id
@GeneratedValue
privateLong id;/**
* The next attribute is embedded directly in me. That means its attributes
* will be directly stored in columns in the same table as me rather than
* being in its own table with key to itself and foreign key back to me.
*/
@Embedded
privateName name;/**
* A book might be written by several authors and an author might write
* several books. Therefore we maintain a many-to-many relationship between
* books authors. It's bidirectional as well.
*/
@ManyToMany
privateSet<Book> booksWritten;public Author(finalName name){
setName(name);}public Author(){}publicSet<Book> getBooksWritten(){return booksWritten;}publicvoid addBook(finalBook b){
booksWritten.add(b);
b.addAuthor(this);}publicvoid setBooksWritten(finalSet<Book> booksWritten){this.booksWritten = booksWritten;}publicLong getId(){return id;}publicvoid setId(finalLong id){this.id = id;}/**
* We are storing Authors in sets so we need to define some definition of
* equality. We've decided to use Name as that definition. You might think
* to use the id field for equality but it may not be assigned before this
* object is placed in a collection so we have to use a more natural
* definition of equality.
*/
@Overridepublicboolean equals(finalObject object){if(object instanceof Author){final Author rhs = (Author) object;return getName().equals(rhs.getName());}returnfalse;}/**
* The hash code should relate to the equals method. And as mentioned there,
* we cannot use the id field for the hash code because it is likely we
* won't have an id already assigned by the database before we try put this
* object in a collection that requires the hashCode method (such as HashSet
* or HashMap). So we use a natural part of the object for its
* interpretation of hash code.
*/
@Overridepublicint hashCode(){return getName().hashCode();}publicName getName(){return name;}publicvoid setName(finalName name){this.name = name;}}
Book
packageentity;importjava.util.Calendar;importjava.util.Date;importjava.util.HashSet;importjava.util.Set;importjavax.persistence.CascadeType;importjavax.persistence.Column;importjavax.persistence.Entity;importjavax.persistence.GeneratedValue;importjavax.persistence.Id;importjavax.persistence.ManyToMany;importjavax.persistence.ManyToOne;importjavax.persistence.NamedQueries;importjavax.persistence.NamedQuery;/**
* I represent a Book. I have one named query to find a book by its isbn number.
* I also have a many to many relationship with author. Since I define the
* mappedBy, I'm the (arbitrarily picked) master of the relationship. I also
* take care of cascading changes to the database.
*/
@EntitypublicclassBook{
@Id
@GeneratedValue
privateLong id;
@Column(length = 100, nullable = false)privateString title;
@Column(length = 20, nullable = false)privateString isbn;privateDate printDate;/**
* Authors may have written several books and vice-versa. We had to pick one
* side of this relationship as the primary one and we picked books. It was
* arbitrary but since we're dealing with books, we decided to make this
* side the primary size. The mappedBy connects this relationship to the one
* that is in Author. When we merge or persist, changes to this collection
* and the contents of the collection will be updated. That is, if we update
* the name of the author in the set, when we persist the book, the author
* will also get updated.
*
* Note that if we did not have the cascade setting here, they if we tried
* to persist a book with an unmanaged author (e.g. a newly created one),
* the entity manager would contain of a transient object.
*/
@ManyToMany(mappedBy = "booksWritten", cascade = { CascadeType.PERSIST,
CascadeType.MERGE})privateSet<Author> authors;/**
* I may be borrowed. If so, then I'll know who that is. In this version, I
* simply have a direct relationship with the Patron. In the next version,
* we'll create a table to capture the details of borrowing a resource.
*/
@ManyToOne
private Patron borrowedBy;publicBook(finalString t, finalString i, finalDate printDate,
final Author... authors){
setTitle(t);
setIsbn(i);
setPrintDate(printDate);for(Author a : authors){
addAuthor(a);}}publicBook(){}publicSet<Author> getAuthors(){if(authors == null){
authors = newHashSet<Author>();}return authors;}publicvoid setAuthors(finalSet<Author> authors){this.authors = authors;}publicLong getId(){return id;}publicvoid setId(finalLong id){this.id = id;}publicString getIsbn(){return isbn;}publicvoid setIsbn(finalString isbn){this.isbn = isbn;}publicDate getPrintDate(){return printDate;}publicvoid setPrintDate(finalDate printDate){this.printDate = printDate;}publicString getTitle(){return title;}publicvoid setTitle(finalString title){this.title = title;}publicvoid addAuthor(final Author author){
getAuthors().add(author);}
@Overridepublicboolean equals(finalObject rhs){return rhs instanceofBook&&((Book) rhs).getIsbn().equals(getIsbn());}
@Overridepublicint hashCode(){return getIsbn().hashCode();}publicboolean wasWrittenBy(Author a){return getAuthors().contains(a);}publicboolean checkedOutBy(Patron p){return p != null&& p.equals(getBorrowedBy());}publicDate calculateDueDateFrom(Date checkoutDate){finalCalendar c = Calendar.getInstance();
c.setTime(checkoutDate);
c.add(Calendar.DATE, 14);return c.getTime();}public Patron getBorrowedBy(){return borrowedBy;}publicvoid setBorrowedBy(Patron borrowedBy){this.borrowedBy = borrowedBy;}}
Name
packageentity;importjavax.persistence.Column;importjavax.persistence.Embeddable;/**
* Rather than repeat first name/last name in both Patron and Author, we create
* an embedded class. The fields of this class end up as columns in the table
* that contains the class that embeds this entity. That is, both author and
* patron will have a firstName and lastName column.
*/
@Embeddable
publicclassName{
@Column(length = 20, nullable = false)privateString firstName;
@Column(length = 30, nullable = false)privateString lastName;publicName(){}publicName(finalString firstName, finalString lastName){
setFirstName(firstName);
setLastName(lastName);}publicString getFirstName(){return firstName;}publicvoid setFirstName(String firstName){if(firstName != null){this.firstName = firstName;}else{this.firstName = "";}}publicString getLastName(){return lastName;}publicvoid setLastName(String lastName){if(lastName != null){this.lastName = lastName;}else{this.lastName = "";}}}
Patron
packageentity;importjava.util.HashSet;importjava.util.Set;importjavax.persistence.CascadeType;importjavax.persistence.Column;importjavax.persistence.Embedded;importjavax.persistence.Entity;importjavax.persistence.GeneratedValue;importjavax.persistence.Id;importjavax.persistence.OneToMany;importjavax.persistence.OneToOne;
@Entitypublicclass Patron {
@Id
@GeneratedValue
privateLong id;
@Embedded
privateName name;
@Column(length = 11, nullable = false)privateString phoneNumber;/**
* This next field refers to an object that is stored in another table. All
* updates are cascaded. So if you persist me, my address, which is in
* another table, will be persisted automatically. Updates and removes are
* also cascaded automatically.
*
* Note that cascading removes is a bit dangerous. In this case I know that
* the address is owned by only one Patron. In general you need to be
* careful automatically removing objects in related tables due to possible
* constraint violations.
*/
@OneToOne(cascade = CascadeType.ALL)private Address address;/**
* A Patron may checkout several books. This collection
*/
@OneToMany(mappedBy = "borrowedBy", cascade = { CascadeType.MERGE,
CascadeType.PERSIST})privateSet<Book> borrowedBooks;public Patron(finalString fName, finalString lName, finalString phone,
final Address a){
setName(newName(fName, lName));
setPhoneNumber(phone);
setAddress(a);}public Address getAddress(){return address;}publicvoid setAddress(Address address){this.address = address;}publicLong getId(){return id;}publicvoid setId(Long id){this.id = id;}publicString getPhoneNumber(){return phoneNumber;}publicvoid setPhoneNumber(String phoneNumber){this.phoneNumber = phoneNumber;}publicSet<Book> getBorrowedBooks(){if(borrowedBooks == null){
borrowedBooks = newHashSet<Book>();}return borrowedBooks;}publicvoid setBorrowedBooks(Set<Book> borrowedBooks){this.borrowedBooks = borrowedBooks;}publicvoid addBook(finalBook b){
getBorrowedBooks().add(b);}publicvoid removeBook(finalBook b){
getBorrowedBooks().remove(b);}publicName getName(){return name;}publicvoid setName(Name name){this.name = name;}}
Note that we did not also include retrieving a book. We use this functionality in all of the tests anyway so I do not include a specific test for that functionality. This might seem like we’re not isolating tests perfectly but then I’ve never seen or come up with a “perfect” solution to this issue and this seems adequate to me.
We've already written a test very much like the above list if you consider PatronTest. We can extract quite a bit of common code out of our PatronTest and reuse it in our BookTest class. Take a look at this base class (note the embedded comments contain background information):
BaseDbDaoTest.java
Now let’s see how this impacts the creation of our new BookTest class. We’ll start with everything but the tests and then look at each test.
Everything but the Tests
Here is the test class minus all of the tests.
Creating a Book
We wrote this pretty much the same as in the Patron test. It might seem like we could get further reuse between tests and we could but at the cost of probably a bit too much indirection.
@Test public void createABook() { final Book b = createABookImpl(); final Book found = getDao().retrieve(b.getId()); assertNotNull(found); } private Book createABookImpl() { final Author a1 = new Author(new Name("Bill", "Burke")); final Author a2 = new Author(new Name("Richard", "Monson-Haefel")); return getDao().create("Enterprise JavaBeans 3.0", "978-0-596-00978-6", Calendar.getInstance().getTime(), a1, a2); }Removing a Book
This test method looks just like one in the PatronTest class. If you’re looking for an advanced exercise, consider moving all of the tests in the base class and making the derived class methods use them somehow. Warning, you might want to look up annotation inheritance.
@Test public void removeABook() { final Book b = createABookImpl(); Book found = getDao().retrieve(b.getId()); assertNotNull(found); getDao().remove(b.getId()); found = getDao().retrieve(b.getId()); assertNull(found); }Updating a Book
@Test public void updateABook() { final Book b = createABookImpl(); final int initialAuthorCount = b.getAuthors().size(); b.addAuthor(new Author(new Name("New", "Author"))); getDao().update(b); final Book found = getDao().retrieve(b.getId()); assertEquals(initialAuthorCount + 1, found.getAuthors().size()); }Try to find a non- existant book
@Test public void tryToFindBookThatDoesNotExist() { final Book b = getDao().retrieve(-1123123123l); assertNull(b); }Note that with the introduction of the base class we’ll also need to make changes to PatronTest. Here’s the updated version of PatronTest taking the new base class into consideration.
PatronDaoTest.java Updated
The Dao Classes
The BookDao looks a whole lot like the PatronDao:BookDao.java
Note that this class depends on a simple base class, the BaseDao, which offers support for storing the Entity Manager attribute:
BaseDao.java
And finally, here’s the updated PatronDao that has been rewritten to use the BaseDao.
PatronDao.java
The Entity Model
We’ve added support for a Book and along the way we had to add in a few more classes. After the second test suite, we’re up to the following entities:Now let’s review the code for each of these entities. As with previous examples, pay attention to the embedded comments.
Address
Author
Book
Name
Patron